Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR prevents Copilot Code Review (CCR) runs from calling the feature flags API (which currently 403s with CCR credentials), and instead always uses default feature flag values to avoid confusing logs and unnecessary API traffic.
Changes:
- Skip the feature flags API request when running in CCR, falling back to default values.
- Update debug messaging for non-dotcom environments to reflect “default values” behavior.
- Extend unit tests to cover the CCR default-values behavior and adjust existing assertions.
Reviewed changes
Copilot reviewed 9 out of 9 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| src/feature-flags.ts | Adds CCR detection to bypass remote feature-flag fetching and updates debug messaging for non-dotcom. |
| src/feature-flags.test.ts | Adds a CCR test case and refactors assertions to validate default-value behavior and expected logs. |
| lib/upload-sarif-action.js | Generated build output reflecting the feature flag behavior changes. |
| lib/start-proxy-action.js | Generated build output reflecting the CCR detection and feature flag behavior changes. |
| lib/setup-codeql-action.js | Generated build output reflecting the CCR detection and feature flag behavior changes. |
| lib/init-action.js | Generated build output reflecting the feature flag behavior changes. |
| lib/init-action-post.js | Generated build output reflecting the feature flag behavior changes. |
| lib/autobuild-action.js | Generated build output reflecting the CCR detection and feature flag behavior changes. |
| lib/analyze-action.js | Generated build output reflecting the feature flag behavior changes. |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
mbg
approved these changes
Feb 12, 2026
Member
This was referenced Feb 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CCR's auth token does not currently have enough permissions to access the features API, so it 403s. This PR skips the API request and uses the default values for all feature flags. This is less confusing in the logs, saves a bit of time, and reduces a bit of API load.
The drawback is we'll need to back this change out once we get round to updating CCR and the features flag API to work together.
Risk assessment
For internal use only. Please select the risk level of this change:
Which use cases does this change impact?
Workflow types:
dynamicworkflows (Default Setup, CCR, ...).Products:
Environments:
github.comand/or GitHub Enterprise Cloud with Data Residency.How did/will you validate this change?
.test.tsfiles).If something goes wrong after this change is released, what are the mitigation and rollback strategies?
How will you know if something goes wrong after this change is released?
Are there any special considerations for merging or releasing this change?
Merge / deployment checklist